Skip to content

fix: the lsdriver kernel module exposes direct physi... in physical.h#3

Open
orbisai0security wants to merge 1 commit into
lsnbm:mainfrom
orbisai0security:fix-v-018-physical-memory-write-access-control
Open

fix: the lsdriver kernel module exposes direct physi... in physical.h#3
orbisai0security wants to merge 1 commit into
lsnbm:mainfrom
orbisai0security:fix-v-018-physical-memory-write-access-control

Conversation

@orbisai0security
Copy link
Copy Markdown

Summary

Fix critical severity security issue in lsdriver/physical.h.

Vulnerability

Field Value
ID V-018
Severity CRITICAL
Scanner multi_agent_ai
Rule V-018
File lsdriver/physical.h:219

Description: The lsdriver kernel module exposes direct physical memory read and write operations to any user who can open the device node. The write operation at physical.h:250 allows writing attacker-controlled data to any physical memory address. Without access restrictions on the device node, a non-root Android user can overwrite kernel security structures such as process credentials (task_struct->cred) or SELinux enforcement flags, granting themselves immediate root privileges without exploiting any memory corruption bug.

Changes

  • lsdriver/physical.h

Verification

  • Build passes
  • Scanner re-scan confirms fix
  • LLM code review passed

Automated security fix by OrbisAI Security

Automated security fix generated by Orbis Security AI
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant